Repository navigation
chore: 0.49.1 - #555
Merged
Merged
chore: 0.49.1#555
Conversation
A static service forwards paths to another server, as a reverse proxy in front of it would: a single-page app that calls its API on its own origin runs as a static build in a profile without a proxy of its own. The start page gets a search, a state filter, small tiles, a list and the sidebar's order menu, and a Shift icon marks the buttons whose confirmation Shift-click skips. 0.49.0 was tagged but not published: the release gate refused a build tool's advisory, and now counts only what the dashboard's bundle holds. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
Release 0.49.1, the content of 0.49.0 (#553), whose tag
v0.49.0stays unpublished: its release workflow refused a build tool's advisory (picomatch), and #554 (ADR-0111) makes the gate count only what the dashboard's bundle holds. As point 4 of #554's card says:Cargo.toml(cargo update -w) andui/package.json/package-lock.json.CHANGELOG.md: the section[0.49.0]becomes[0.49.1], its summary says 0.49.0 was tagged but not published; compare links fromv0.48.0tov0.49.1.docs/plan.md: status line and the §7.4 paragraph as 0.49.1.devstack.toml:reviewed = "0.49.1";devstack checkclean.FORWARD_SINCEstays0.49.0(0.49.1 satisfies it).Checked
ui/scripts/audit-shipped.mjsafternpm run buildpasses (23 packages in the bundle, picomatch not among them);cargo deny --all-features check advisoriesok;scripts/release-notes.sh 0.49.1renders the summary.release.ymlas a dry run with the new gate: every platform built.🤖 Generated with Claude Code